generate java pojo from json

Source: http://user.qzone.qq.com/31584 (QQ space) Http:// B .qzone.qq.com/cgi-bin/blognew/blog_output_data? Uin = 31584 blogid = 1254066496 styledm = Hangzhou imtpd = qzs.qq.com BDM = B .qzone.qq.com mode = 2 numperpage = 15 blogseed = 0.29501750965040874 property = Gore timestamp = 1273108734 (actual address) Pojo = pure old Java object or plain ordinary

, the Po and Vo, their relationship should be independent of each other, a VO can be just a PO part, also can be a number of PO composition, the same can also be equated to a PO (of course I refer to their attributes). Because of this, the PO is independent, the data persistence layer is independent, it will not be interfered by any business. Because of this, the business logic layer is also independent, it will not be affected by the data persistence layer, the business layer is only concerned

course I mean their attributes ). As a result, the PO is independent, and the data persistence layer is independent, so it is not subject to any business interference. In this case, the business logic layer is also independent and will not be affected by the data persistence layer. The business layer only cares about the processing of the business logic. As for how to read and give it to others! However, if we do not use the data persistence layer or hibernate, Po and VO can be the same thing,

/set method, but for hibernate, this requires special attention, because hibernate from the database read data to do, is to use the reflection mechanism to call do the empty argument constructor to construct a do instance, Then using the JavaBean specification to reflect the set method to set a value for each property, if you do not explicitly declare the set method, or set method to private, will cause hibernate to fail to initialize do, resulting in a run-time exception, It is advisable to set

The Java (Po,vo,to,bo,dao,POJO) explanation for the O/R Mapping is an abbreviation for Object Relational Mapping ( the Objects relational map). The popular point is that the object is bound to the relational database, and the object is used to represent the relational data. 　　In the world of O/R Mapping, there are two basic and important things to understand, namely Vo,po. VO, a Value object, a PO, a pe

Po (persistant object) Persistent ObjectThe concept that appears during o/R ing does not exist if there is no o/R ing. usually it corresponds to the data model (database), and some business logic is processed. it can be seen as a Java object mapped to tables in the database. the simplest Po is to correspond to a record in a table in the database. A set of PO can be used for multiple records. the PO should not contain any database operations. VO (Val

POJO is the most common and variable object. It is an intermediate object and the most common object to deal.After a POJO is persisted, it is the POIt is DTO in the process of passing and passing.Directly used to correspond to the presentation layer is VODAO:Data access objectThis person is the most familiar with it. It is the most different from the previous O, and there is basically no possibility or nee

one, PO:(persistant object), Persistent objectsCan be seen as a Java object mapped to a table in the Database. Using hibernate to generate a PO is a good choice.second, VO:(value object), value ObjectsTypically used for data transfer between business tiers, as is the case with po, which contains only Data. But it should be abstracted out of business objects that can correspond to tables, or not, depending o

One, PO:(persistant object), persistent objectsCan be seen as a Java object mapped to a table in the database. Using hibernate to generate a PO is a good choice.Second, VO:(value object), Value objectsTypically used for data transfer between business tiers, as is the case with PO, which contains only data. But it should be abstracted out of business objects that can correspond to tables, or not, depending o